| 1. | Disables the keeping of cpu time and cache - hit ratio statistics 不保留cpu时间和高速缓存命中率统计信息。 |
| 2. | Hit ratios should be high 命中率应该高 |
| 3. | Indexes in particular should have a high hit ratio to ensure good performance 特别是索引应该有较高的命中率,以确保良好的性能 |
| 4. | Package and catalog caches , and workspaces for example , package cache hit ratio 包与目录缓存,以及工作空间(如包高速缓冲区命中率) 。 |
| 5. | For certain workloads cache hit ratio is lower than would justify having it enabled 在一定的负载压力下,如果缓存命中率太低了,就启用它。 |
| 6. | Cache api hit ratio the cache hit - to - miss ratio when accessed through the external cache apis 当通过外部缓存api访问时,缓存命中数与未命中数的比率。 |
| 7. | Additionally , more rows fit in the storage engine cache , potentially improving the hit ratio 此外,存储引擎缓存中也可以包含更多的行,而这可能会提高命中率。 |
| 8. | Once you know your typical hit ratio this is something you can ultimately delegate to a virtual assistant 一旦你知道你这是典型的命中率最终可以授予一个虚拟助手 |
| 9. | Lower bounded indicators are identified as unhealthy as they decrease in value for example , the cache hit ratio indicator 当设有下界的指示器(例如,缓存命中率指示器)的值降低时,它将标识为不健康。 |
| 10. | You see various graphs that show the details which you might want to monitor such as the buffer pool hit ratio , failed sql statements , and sort overflows 图4中,您可以看到各种显示您可能想要监控的细节的图,例如缓冲池利用率、失败的sql语句和排序溢出。 |